Sprint Retrospective Oct 22
| Doc Type | Retrospective |
|---|
Sprint Retrospective Meeting Minutes
Project: Learnr
Attendees: Rose, Amani
Start time: 6:30 PM
End time: 7:00 PM
What went wrong?
- Did we do a good job estimating our team's velocity?
- Yes, we did! We performed a conservative estimation at the beginning of the sprint, and over performed.
- Did we do a good job estimating the points (time required) for each user story?
- Yes, our estimation even out. We both overestimated and underestimated in certain user stories, which evened out to be just right.
- Did each team member work as scheduled?
- Yes, they did.
What went right?
- Communication, collaboration, cooperation. Triple C strength!
How to address the issues in the next sprint?
- How to improve the process?
- Increase external feedback on tech stack and software engineering decisions.
- How to improve the product?
- User Experience Enhancement:
- Redesign the Website: Transition from basic HTML and early 80’s minimalistic styling to an intuitive, immersive design reflective of our brand.
- Develop a Home Page: Design a captivating home page to serve as the central hub for user engagement and information dissemination.
- Backend Revamp:
- Code Cleanup: Simplify and restructure the existing "code spaghetti" for clarity and efficiency.
- Adopt Best Practices: Focus on data security, robust architecture, and up-to-date software engineering principles to ensure a solid foundation for our product.
- User Experience Enhancement: